[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chrischdi for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

This PR is currently missing an area label, which is used to identify the modified component when generating release notes.

Area labels can be added by org members by writing /area ${COMPONENT} in a comment

Please see the labels list for possible areas.

PR needs rebase.

@sbueringer: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

so in short are we aiming to refactor conversion logic to make zz_* generated files more generic across the project (which would solve etcd issues mentioned such as old object vs new object in the KV store) especially if we're talking external apis - does it relate to kubernetes-sigs/controller-runtime#3335?

And real qeustion is going to be how to properly convert Changed Resource Versions issues for external apis since there is not straight forward of doing this due to the state, so it seems as the effort for modularization in a form of submodules.
Would be nice to avoid creation these kind of PRs manually as they affect tests mostly quite often being simply not synchronized with latest changes - internal vs external conversion should, imo, stay separate which, correct if wrong, this is being progressively achieved.

I'd look at tests deeper to make sure they are properly adopted since quite of a logic was moved but I agree 100 that addons should be separate for the user.